home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.c++
- Path: in1.uu.net!world!mv!usenet
- From: ENGR@GSSI.MV.COM (Michael Furman)
- Subject: Re: malloc() function and new operator
- Message-ID: <DpLKGo.MG0@mv.mv.com>
- Mime-Version: 1.0
- Content-Type: Text/Plain; charset=US-ASCII
- Organization: GSSI
- Date: Tue, 9 Apr 1996 13:36:23 GMT
- References: <4kbo18$t1s@news.NetVision.net.il>
- X-Newsreader: WinVN 0.99.7
- X-Nntp-Posting-Host: gssi.mv.com
-
- In article <4kbo18$t1s@news.NetVision.net.il>,
- nir@netvision.net.il says...
- >
- >I use in my C/C++ programs both malloc() function and new
- operator.
- >i use new and delete operators for objects and malloc() and
- free()
- >functions for allocating strings and other variables.
- >
- >i compile my programs with Borland C++ 4.0
- >it works fine, but i want to be sure that i'm not doing
- something
- >wrong that will cause troubles in the future.
- >
- >Is it o.k to use both of them in the same program ?
-
- Nothing wrong, but I don't see any reason for using
- malloc/free in C++
- (except only case if you are using realloc that does not
- have C++
- equivalent).
- --
- <<< If you received it by E-mail: it is a copy of post to
- the newsgroup >>>
- ------------------------------------------------------------
- ---
- Michael Furman, (603)893-1109
- Geophysical Survey Systems, Inc. fax:(603)889-3984
- 13 Klein Drive - P.O. Box 97 engr@gssi.mv.com
- North Salem, NH 03073-0097
- 71543.1334@compuserve.com
- ------------------------------------------------------------
- ---
-
-